Computer-based systems configured to provide a portal for migrating one or more existing relationships from one entity to another entity and methods of use thereof

ABSTRACT

Systems and methods associated with providing an automated portal to migrate one or more relationships with one entity to another entity are disclosed. In one embodiment, an exemplary method may comprise: providing a portal enabling automated migration of existing relationships from existing entities to a first entity; generating a first UI configured for identifying and providing access information regarding existing relationships for potential migration; generating a second UI to display information regarding the existing relationships and provide UI elements enabling the user to receive migration offers; determining terms of replacement relationships that the first entity can offer the user; generating a third UI to (i) compare terms between the existing and new relationships, and (ii) enable the user to authorize the relationship migration; performing an automated generation process to create the new relationship(s); and performing an automated transfer process to transfer all objects to the new relationship.

COPYRIGHT NOTICE

A portion of the disclosure of this patent document contains materialthat is subject to copyright protection. The copyright owner has noobjection to the facsimile reproduction by anyone of the patent documentor the patent disclosure, as it appears in the Patent and TrademarkOffice patent files or records, but otherwise reserves all copyrightrights whatsoever. The following notice applies to the software and dataas described below and in drawings that form a part of this document:Copyright, Capital One Services, LLC., All Rights Reserved.

FIELD OF TECHNOLOGY

The present disclosure generally relates to an improved computer-basedplatform or system, improved computing components and devices and/orimproved computing methods configured for one or more noveltechnological applications involving a platform with portals comprisingfeatures and functionality for migrating one or more existingrelationships or accounts from one entity to another entity.

BACKGROUND OF TECHNOLOGY

A computer network platform or system may include a group of computers(e.g., clients, servers, smart routers, etc.) and other computinghardware devices that are linked together through one or morecommunication channels to facilitate communication, relationship oraccount management, and/or electronic handling related to same.

SUMMARY OF DESCRIBED SUBJECT MATTER

In some embodiments, the present disclosure provides various exemplarytechnically improved computer-implemented methods associated withproviding an automated portal to migrate one or more relationships withone entity to another entity, including methods having steps such as:

providing, by at least one computer associated with a first entity, aportal by which a user may be provided functionality to migrate, to thefirst entity, one or more existing relationships that the user has withone or more second entities;

generating, by the at least one computer, to provide to the user, afirst UI configured to:

-   -   (i) display one or more first UI elements that enable the user        to specify the one or more existing relationships that the user        may wish to migrate to the first entity, and    -   (ii) provide one or more fields into which the user enters        access information that enables direct electronic access, by the        first entity, to objects representing the one or more existing        relationships;

generating, by the at least one computer, to provide to the user, asecond UI configured to:

-   -   (i) display one or more relationship types and associated        relationship information regarding the one or more existing        relationships that the user may wish to migrate, and    -   (ii) provide one or more second UI elements configured to allow        the user to select at least one element representing the one or        more existing relationships with respect to which the user        desires to receive offer information regarding potential        migration;

determining by the at least one computer, new relationship terms of oneor more new relationships that the first entity can offer the user, theone or more new relationships corresponding to the one or more existingrelationships that the user selected for the potential migration to thefirst entity;

generating, by the at least one computer, to provide to the user, athird UI configured to:

-   -   (i) display a comparison view illustrating the new relationship        terms of the one or more new relationships compared against        existing relationship terms of the one or more existing        relationships that the user selected for potential migration,        and    -   (ii) provide one or more third UI elements selection of which by        the user confirms that the user authorizes relationship        migration to proceed for selected ones of the at least one        element representing the one or more existing relationships        selected for potential migration;

upon receipt of the at least one element selected representing the oneor more existing relationships, performing, by the at least onecomputer, an automated relationship generation process that creates theone or more new relationship authorized via user-selection of the one ormore third UI elements; and

automatically performing a transfer process, by the at least onecomputer accessing at least one application programming interface (API)of at least one computer platform associated with the second entities,via an external network connection, including:

-   -   (i) generating electronic requests to transfer all objects        associated with a respective existing relationship to the first        entity;    -   (ii) associating the transferred objects with a respective new        relationship associating with the second entity; and    -   (iii) confirming that the transferred objects have been        transferred; and

automatically causing, by the at least one computer, a relationshiptermination process of the one or more existing relationship toterminate each respective transferred existing relationship with thesecond entity that was successfully transferred to the first entity.

In some embodiments, the present disclosure also provides exemplarytechnically improved computer-based systems and computer-readable media,including media implemented with and/or involving one or more softwareapplications, whether resident on computer devices or platforms,provided for download via a server and/or executed in connection with atleast one network such as via a web application, that include orinvolves features, functionality, computing components and/or stepsconsistent with any set forth herein.

BRIEF DESCRIPTION OF THE DRAWINGS

Various embodiments of the present disclosure can be further explainedwith reference to the attached drawings, wherein like structures arereferred to by like numerals throughout the several views. The drawingsshown are not necessarily to scale, with emphasis instead generallybeing placed upon illustrating the principles of the present disclosure.Therefore, specific structural and functional details disclosed hereinare not to be interpreted as limiting, but merely as a representativebasis for teaching one skilled in the art to variously employ one ormore illustrative embodiments.

FIG. 1 is a block diagram of an exemplary system and/or platformincluding aspects associated with migration of relationships oraccounts, consistent with exemplary aspects of certain embodiments ofthe present disclosure.

FIG. 2 is a block diagram of an exemplary system and/or platforminvolving features associated with migration of relationships oraccounts, consistent with exemplary aspects of certain embodiments ofthe present disclosure.

FIG. 3 is a block diagram of an exemplary computing device that may beassociated with migration of relationships or accounts, consistent withexemplary aspects of certain embodiments of the present disclosure.

FIG. 4 is a block/flow diagram illustrating one exemplary system andrelated process related to performing migration of one or morerelationships or accounts from one entity to another entity, consistentwith exemplary aspects of certain embodiments of the present disclosure.

FIG. 5 is a diagram illustrating one exemplary process flow related toperforming migration of one or more relationships or accounts from oneentity to another entity, consistent with exemplary aspects of certainembodiments of the present disclosure.

FIG. 6 is a flowchart illustrating one exemplary process related toproviding a portal that performs migration of one or more relationshipsor accounts, consistent with exemplary aspects of certain embodiments ofthe present disclosure.

FIGS. 7A-7K are diagrams illustrating various exemplary user interfaces,features and functionality for performing migration of one or morerelationships or accounts, consistent with exemplary aspects of certainembodiments of the present disclosure.

FIG. 8 is a block diagram depicting an exemplary computer-based systemand/or platform, in accordance with certain embodiments of the presentdisclosure.

FIG. 9 is a block diagram depicting another exemplary computer-basedsystem and/or platform, in accordance with certain embodiments of thepresent disclosure.

FIGS. 10 and 11 are diagrams illustrating two exemplary implementationsof cloud computing architecture/aspects with respect to which thedisclosed technology may be specifically configured to operate, inaccordance with certain embodiments of the present disclosure.

DETAILED DESCRIPTION

Various detailed embodiments of the present disclosure, taken inconjunction with the accompanying figures, are disclosed herein;however, it is to be understood that the disclosed embodiments aremerely illustrative. In addition, each of the examples given inconnection with the various embodiments of the present disclosure isintended to be illustrative, and not restrictive.

Throughout the specification, the following terms take the meaningsexplicitly associated herein, unless the context clearly dictatesotherwise. The phrases “in one embodiment” and “in some embodiments” asused herein do not necessarily refer to the same embodiment(s), thoughit may. Furthermore, the phrases “in another embodiment” and “in someother embodiments” as used herein do not necessarily refer to adifferent embodiment, although it may. Thus, as described below, variousembodiments may be readily combined, without departing from the scope orspirit of the present disclosure.

Aspects of the present innovations relate to a computer-generated portalcomprising user interfaces configured to migrate one or morerelationships or accounts a user has with one entity to another entityare disclosed. In one embodiment, an exemplary method may comprise:providing a portal enabling automated migration of existingrelationships from existing entities to a first entity; generating afirst UI configured for identifying and providing access informationregarding existing relationships for potential migration; generating asecond UI to display information regarding the existing relationshipsand provide UI elements enabling the user to receive migration offers;determining terms of replacement relationships that the first entity canoffer the user; generating a third UI to (i) compare terms between theexisting and new relationships, and (ii) enable the user to authorizethe relationship migration; performing an automated generation processto create the new relationship(s); and performing an automated transferprocess to transfer all objects to the new relationship. Further,aspects of the innovations herein may involve various technicalsolutions required for communications between and utilization ofdifferent software applications associated with the first entity.Additional details regarding such technical solutions, including but notlimited to the portal's interactions with application programminginterfaces (APIs), are described herein, for example, in connection withFIG. 5 and elsewhere below.

FIG. 1 is a block diagram of an exemplary system and/or platform 100involving features of migrating relationships or accounts as well asgenerating and displaying associated user interfaces, in accordance withat least some disclosed embodiments. System 100 may be configured forexecuting one or more software applications, such as an applicationinvolving a portal for performing an automated migration process(hereafter “portal application”) such as via an associated network/webapplication, consistent with disclosed embodiments. As shown, system 100may include a computing device 102, such as a client computing device,associated with a user 104. Computing device 102 may be configured toexecute, among other programs, a network/web application 108 and aportal application or portal subcomponent 111. System 100 may furtherinclude a first entity computer or system 110 such as an entity thatprovides a portal application 109 for performing migration herein, andone or more second entities 114 at which the user has one or morerelationships or accounts 112. As shown, computing device 102, firstentity 110, and second entities 114, may be communicatively coupled by anetwork 116. Various features, functionality and benefits of portalapplication 109 may also be achieved via one or more portal applicationsor subcomponents 111 (hereafter “modules”) within or executed by theclient computing device 102. For simplicity of explanation, the behaviorof such software applications and/or subcomponents (i.e., 109 and 111)are generally discussed below by referring to just the “portalapplication.”

While only one computing device 102, first entity 110, and network 116are shown, it will be understood that system 100 may include more thanone of any of these components. More generally, the components andarrangement of the components included in system 100 may vary. Thus,system 100 may include other components that perform or assist in theperformance of one or more processes consistent with the disclosedembodiments. Computing device 102 may be one or more computing devicesconfigured to perform operations consistent with executing the portalapplication 111 and/or the network/web application 108. One illustrativecomputing device 102 is further described below in connection with FIG.3.

Network/web application 108 may be one or more software applicationsconfigured to perform operations consistent with providing network orweb pages to the user 104, accessing the portal (via network or online),as set forth herein, as well as interacting with the portal application109, and the like. Here, for example, network/web application 108 may beconfigured to provide various user interfaces and information,associated with accessing pages related to the user's 104 activity withthe portal. Such processing may occur by or with a network/webapplication 108, locally, or the network/web application 108 maytransmit requests to and/or operate with one or more other softwareapplications and/or computing components to process the desiredinformation. Network/web application 108 may also be hosted and/oroperated, in whole or in part, by a network/web system and/or server,described below in connection with FIG. 2. Network/web application 108is further described below in connection with FIG. 3.

Portal application 111 may be one or more software applications,modules, routines, subroutines and/or extensions configured to performoperations consistent with accessing, using and/or providing informationrelated to the portal application 109 provided by or in associate withthe first entity 110, such as the features and functionality associatedwith the user interfaces shown and discussed further in connection withFIGS. 7A-7K.

First entity 110 may be an entity associated with one or more computingdevices that are being operated to provide the portal application as athird-party provider (e.g., outside institution, software as a service,etc.). However, the portal application 109 may also be providedinternally by an entity wishing to provide such portal to its customersor members.

Second entities 114 may each comprise one or more computing devicesconfigured to perform operations consistent with providing relationshipsor accounts to the user, including features and functionality accessibleby computing device 102 over network 116. For example, network or webpages of the second entities 114 may be provided at computing device 102via the network/web application 108. The disclosed embodiments are notlimited to any particular configuration of second entities 114.

In some embodiments, first entity 110 and second entities 114 may eachbe associated with a financial service entity that provides, maintains,manages, or otherwise offers financial services. For example, thefinancial service entity may be a bank, credit card issuer, or any othertype of financial service entity that generates, provides, manages,and/or maintains financial service accounts for one or more customers.Financial service accounts may include, for example, credit cardaccounts, loan accounts, checking accounts, savings accounts, reward orloyalty program accounts, and/or any other type of financial serviceaccount known to those skilled in the art.

Network 116 may be any type of network configured to providecommunication between components of system 100. For example, network 116may be any type of network (including infrastructure) that providescommunications, exchanges information, and/or facilitates the exchangeof information, such as the Internet, a Local Area Network, near fieldcommunication (NFC), optical code scanner, or other suitableconnection(s) that enables the sending and receiving of informationbetween the components of system 100. In other embodiments, one or morecomponents of system 100 may communicate directly through a dedicatedcommunication link(s).

It is to be understood that the configuration and boundaries of thefunctional building blocks of system 100 have been defined herein forthe convenience of the description. Alternative boundaries can bedefined so long as the specified functions and relationships thereof areappropriately performed. Alternatives (including equivalents,extensions, variations, deviations, etc., of those described herein)will be apparent to persons skilled in the relevant art(s) based on theteachings contained herein. Such alternatives fall within the scope andspirit of the disclosed embodiments.

FIG. 2 is a block diagram of an exemplary network/web system 200, inaccordance with at least some disclosed embodiments. As shown,network/web system 200 may include network/web server 202 andnetwork/web application 204. Network/web server 202 may include acommunication device 206, one or more processor(s) 208, and memory 210including one or more programs 212 and data 214. Network/web server 202may be configured to perform operations consistent with providing aportal, user interfaces, features and functionality of the portalapplication 109 over one or more networks, such as an organization'sintranet, the World Wide Web, etc., to the user 104.

Network/web server 202 may take the form of a server, general purposecomputer, mainframe computer, or any combination of these components.Other implementations consistent with disclosed embodiments are possibleas well. Network/web application 204 may take the form of one or moresoftware applications stored on a computing device, such as network/webapplication 108 stored on computing device 102 described above.

Communication device 206 may be configured to communicate with one ormore computing devices, such as computing device 102. In someembodiments, communication device 206 may be configured to communicatewith the computing device(s) through network/web application 204.Network/web server 202 may, for example, be configured to provideinstructions and/or operating information to network/web application 204through communication device 206. Communication device 206 may beconfigured to communicate other information as well.

Communication device 206 may be further configured to communicate withone or more entities, including the first entity 110 and the secondentities 114, described above. Communication device 206 may beconfigured to communicate with such entities in other manners.

Communication device 206 may be configured to communicate with othercomponents as well.

Processor(s) 208 may include one or more known processing devices, suchas a microprocessor from the Core™, Pentium™ or Xeon™ familymanufactured by Intel®, the Turion™ family manufactured by AMD™, the“Ax” (i.e., A6 or A8 processors) or “Sx” (i.e. S1, . . . processors)family manufactured by Apple™, or any of various processors manufacturedby Sun Microsystems, for example. The disclosed embodiments are notlimited to any type of processor(s) otherwise configured to meet thecomputing demands required of different components of network/web system200.

Memory 210 may include one or more storage devices configured to storeinstructions used by processor(s) 208 to perform functions related todisclosed embodiments. For example, memory 210 may be configured withone or more software instructions, such as program(s) 212, that mayperform one or more operations when executed by processor(s) 208. Suchoperations may include network/web activities as well as creation and/ortransmission of related network/web attribute information. The disclosedembodiments are not limited to separate programs or computers configuredto perform dedicated tasks. For example, memory 210 may include a singleprogram 212 that performs the functions of network/web system 200, orprogram(s) 212 may comprise multiple programs. Memory 210 may also storedata 214 that is used by program(s) 212.

In certain embodiments, memory 210 may store one or more sets ofinstructions involved with carrying out the processes described below inconnection with FIGS. 4-7K. Other instructions are possible as well. Ingeneral, instructions may be executed by processor(s) 208 to perform oneor more processes consistent with disclosed embodiments. In someembodiments, program(s) 212 may include one or more subcomponentsconfigured to generate and/or process instructions and information foruse by network/web application 204 in performing interactions and otheractivities associated with accessing the portal application 109.

The components of network/web system 200 may be implemented in hardware,software, or a combination of both hardware and software, as will beapparent to those skilled in the art. For example, although one or morecomponents of network/web system 200 may be implemented as computerprocessing instructions, all or a portion of the functionality ofnetwork/web system 200 may be implemented instead in dedicatedelectronics hardware. In some embodiments, network/web system 200 mayalso be communicatively connected to one or more database(s) (notshown). Alternatively, such database(s) may be located remotely fromnetwork/web system 200. Network/web system 200 may be communicativelyconnected to such database(s) through a network, such as network 116described above. Such database(s) may include one or more memory devicesthat store information and are accessed and/or managed throughnetwork/web system 200. By way of example, such database(s) may includeOracle™ databases, Sybase™ databases, or other relational databases ornon-relational databases, such as Hadoop sequence files, HBase, orCassandra. Such database(s) may include computing components (e.g.,database management system, database server, etc.) configured to receiveand process requests for data stored in memory devices of thedatabase(s) and to provide data to the database(s).

FIG. 3 is a block diagram of an exemplary computing device 300,consistent with disclosed embodiments. As shown, computing device 300may include communication device 302, display device 304, processor(s)306, and memory 308 including program(s) 310 and data 312. Program(s)310 may include, among others, network/web application 314 and portalapplication or subcomponent 316. In some embodiments, computing device300 may take the form of a desktop or mobile computing device, such as adesktop computer, laptop computer, smartphone, tablet, or anycombination of these components. Alternatively, computing device 300 maybe configured as any wearable item, including jewelry, smart glasses, orany other device suitable for carrying or wearing on a person. Otherimplementations consistent with disclosed embodiments are possible aswell. Computing device 300 may, for example, be the same as or similarto computing device 102 described above.

In the example embodiment shown, communication device 302 may beconfigured to communicate via one or more networks with the variouscomputer systems and servers disclosed elsewhere herein. In someembodiments, communication device 302 may be further configured tocommunicate with one or more entities, such as the first entity 110 andthe second entities 114 described above. Communication device 302 may beconfigured to communicate with other components as well. Communicationdevice 302 may be configured to provide communication over a network,such as network 116 described above. To this end, communication device302 may include, for example, one or more digital and/or analog devicesthat allow computing device 300 to communicate with and/or detect othercomponents, such as a network controller and/or wireless adaptor forcommunicating over the Internet. Other implementations consistent withdisclosed embodiments are possible as well.

Display device 304 may be any display device configured to displayinterfaces on computing device 300. The interfaces may include, forexample, network and/or web pages provided by computing device 300through network/web application 108. In some embodiments, display device304 may include a screen for displaying a graphical and/or text-baseduser interface, including but not limited to, liquid crystal displays(LCD), light emitting diode (LED) screens, organic light emitting diode(OLED) screens, and other known display devices. In some embodiments,display device 304 may also include one or more digital and/or analogdevices that allow a user to interact with computing device 300, such asa touch-sensitive area, keyboard, buttons, or microphones. Other displaydevices are possible as well. The disclosed embodiments are not limitedto any type of display devices otherwise configured to displayinterfaces.

Processor(s) 306 may include one or more known processing devices, suchas a microprocessor from the Core™, Pentium™ or Xeon™ familymanufactured by Intel™, the Turion™ family manufactured by AMD™, the“Ax” or “Sx” family manufactured by Apple™, or any of various processorsmanufactured by Sun Microsystems, for example. Processor(s) 306 may alsoinclude various architectures (e.g., x86 processor, ARM®, etc.). Thedisclosed embodiments are not limited to any type of processor(s)otherwise configured to meet the computing demands required of differentcomponents of computing device 300.

Memory 308 may include one or more storage devices configured to storeinstructions used by processor(s) 306 to perform functions related todisclosed embodiments. For example, memory 308 may be configured withone or more software instructions, such as program(s) 310, that mayperform one or more operations when executed by processor(s) 306. Thedisclosed embodiments are not limited to separate programs or computersconfigured to perform dedicated tasks. For example, memory 308 mayinclude a single program 310 that performs the functions of computingdevice 300, or program(s) 310 may comprise multiple programs. Memory 308may also store data 312 that is used by program(s) 310. In certainembodiments, memory 308 may store sets of instructions for carrying outsome processes performed in connection with FIG. 4. Other instructionsare possible as well. In general, instructions may be executed byprocessor(s) 306 to perform one or more processes consistent withdisclosed embodiments.

In some embodiments, program(s) 310 may include a network/webapplication 314. Network/web application 314 may be executable byprocessor(s) 306 to perform operations including, for example, providingpages associated with a software application for display. Such pages maybe provided, for example, via display device 304. In some embodiments,the pages may be associated with a portal being provided by an entity,such as first entity 110, second entities 114, and the like, describedabove. Network/web application 314 may be executable by processor(s) 306to perform other operations as well. In some embodiments, program(s) 310may further include a portal application or subcomponent 316. Portalapplication 316 may, for example, be the same as similar to portalapplications 109 and/or 111, described above. In general, instructionsmay be executed by processor(s) 306 to perform one or more processesconsistent with disclosed embodiments.

The components of computing device 300 may be implemented in hardware,software, or a combination of both hardware and software, as will beapparent to those skilled in the art. For example, although one or morecomponents of computing device 300 may be implemented as computerprocessing instructions, all or a portion of the functionality ofcomputing device 300 may be implemented instead in dedicated electronicshardware.

FIG. 4 is a block/flow diagram illustrating a representative system aswell as an exemplary process for performing migration of one or morerelationships or accounts from one entity to another entity, consistentwith exemplary aspects of certain embodiments of the present disclosure.FIG. 4 depicts a block diagram that illustrates exemplary partiesinvolved with the innovations herein as well as a representative seriesof interactions 420 among the parties. The representative parties shownin FIG. 4 include the user 410 who is considering migration of theirrelationships or accounts from one entity to another, the first entity405 to which the one or more relationships or accounts of the user arebeing migrated, and the second entity 415 from which the relationshipsor accounts are being migrated. FIG. 4 also depicts an exemplary seriesof interactions 420 among the parties, the interactions beingillustrated in connection with a migration request at 425, handling ofexisting bank credentials at 430, account creation at 435, transfer ofrelationships or accounts at 440, and initiation of account deletion at445. In one embodiment, the series of interactions 420 of the exemplaryrelationship or account migrations shown in FIG. 4 may be performed viathe migration portal 109 described above on connection with FIGS. 1-3.

Referring to FIG. 4, the exemplary series of interactions 420illustrated may comprise the user initiating a migration request, at426, with the first entity 405, after which the first entity 405 thenreceiving the migration request, at 427. In the embodiment illustrated,the first entity 405 then initiates a request for the existing bankcredentials from the user, at 431, which the user may then provide, at432, as described in more detail, below. Once the credentials areprovided, the first entity 405 logs into the bank account of the user atthe second entity, wherein the second entity 415 authenticates thelogin, at 433. Next, the first entity may execute an account creationprocess, at 436, such as by generating a new account that the firstentity proposes as a replacement for the existing account. The newaccount and associated terms are then displayed to the user, asexplained in more detail below, whereupon the user 410 next approves thenew account, at 437, if the terms are acceptable. Once the new accountis approved and created, the first entity 405 then initiates or issues atransfer request to transfer all existing assets at the existing accountto the new account. The transfer request is then presented to the user410, who may then accept the transfer request, at 442. Informationregarding the user-approved transfer request is then provided to thesecond entity 415, which approves and/or facilitates the transfer of theassets to the first entity, at 443. Once the assets have beentransferred, the first entity 405 then initiates an existing accountdeletion process, at 446, which is received and approved by the user, at447. The second entity 448 then receives the information or instructionsto delete the existing account, at 448, where the instructions may begenerated by one or both of the first entity 405 and/or the user 410 (asexplained in more detail, below), and then closes/deletes the existingaccount, which, in some embodiments, helps avoid any further charges orfinancial responsibilities from being incurred by the user under the oldaccount.

FIG. 5 is a diagram illustrating one exemplary process flow related toperforming migration of one or more relationships from one entity toanother entity, consistent with exemplary aspects of certain embodimentsof the present disclosure. FIG. 5 illustrates a variety of exemplarycomputerized applications associated with the migration innovationsherein, including a migration portal 505, one or more APIs (applicationprogramming interfaces) 510 enabling communications between entitiessuch as banks, an application and/or server associated withopening/processing new accounts (“new account application”) 515, afinancial services application that conducts transactions with externalentities 520, and a second entity 525 such as another bank and/or other,eternal computer server, system or platform associated with a secondentity separate from the first entity. Below each of these applications(505-525), FIG. 5 also illustrates an exemplary process flow associatedwith various relationship or account migration features herein.

Referring to FIG. 5, the process flow begins upon initiation of themigration process, at 530, where the migration portal commences themigration process by interacting with the user, as described above inconnection with FIG. 4 as well as further below. Once the migrationportal 505 obtains the information regarding the external, existinginstitutions at which the user has relationships or accounts (see, e.g.,step 432 in FIG. 4), the migration portal 505 initiates, at 535,communications with one or more APIs 510 in effort to determine whetheror not the third parties (second entities) of interest are available forelectronic transactions with the first entity. After the first entityverifies communication with the second entities of interest, the APIs510 will return a list of the institutions or banks for which migrationis supported, at 540. Using the login credentials provided by the user,the migration portal 505 next accesses the APIs to obtain the useraccount and/or profile information, at 545, and returns informationrelevant to the migration, at 550, such as account, terms, and balanceinformation. Once the user has approved creation of one or more newaccounts to replace their existing accounts (see, e.g., step 437 in FIG.4), the migration portal interacts, at 555, with the new accountapplication 515 to create the new, approved accounts at the first entitycorresponding to the existing accounts being replaced. The new accountapplication 515 then responds to the migration portal 505, to confirmthat the new accounts are open, at 560. Next, the migration portalinitiates communication with the financial services application thatconducts transactions, such as financial transactions like balancetransfers, with external entities 520 and issues instructions totransfer assets, such as account balances, to the first entity. Once theassets have been transferred, the financial services application 520responds to the migrations portal, at 570, to confirm that the transferis complete. Next, the migration portal can initiate a terminationprocess, at 575, to close the existing accounts in favor of thenewly-created accounts. Communication to terminate the old accounts issent to the second entity 525, such as the external bank, which willthen issue a reply confirming that the accounts have been closed, at580. While such account termination may be initiated by the migrationportal, in some embodiments, the termination may also involve and/orrequire action taken by the user to close the accounts.

FIG. 6 is a flowchart illustrating one exemplary process related toproviding a portal that performs migration of one or more relationshipsor accounts, consistent with exemplary aspects of certain embodiments ofthe present disclosure. Referring to the exemplary embodiment of FIG. 6,an illustrative migration method 600 for migrating one or more existingrelationships or accounts from an existing entity to a new entity maycomprise: providing a portal by which a user may be providedfunctionality to migrate, to a first entity, one or more existingrelationships that the user has with one or more second entities 602;generating, for provision to the user, a first UI configured foridentifying and providing access information regarding existingrelationships for potential migration to the first entity 604;generating a second UI for (i) displaying relationship informationregarding the existing relationships, and (ii) providing UI elementsthat enable the user to receive migration offers for selectedrelationships 606; determining new relationship terms of newrelationship(s) that the first entity can offer the user correspondingto the selected relationships 608; generating a third UI configured to:(i) display a comparison of terms between the existing and newrelationships, and (ii) provide a UI element for the user to authorizethe relationship migration 610; performing an automated relationshipgeneration process to create the new relationship(s) 612; performing anautomated transfer process to transfer all objects to the newrelationship 614; and automatically causing a relationship terminationprocess of the existing relationship(s) that are migrated 614.

According to embodiments herein, in the step of generating, forprovision to the user, a first UI configured for identifying andproviding access information regarding existing relationships (e.g.,accounts) for potential migration to the first entity 604, the first UImay be configured to: (i) display one or more first UI elements thatenable the user to specify the one or more existing relationships thatthe user may wish to migrate to the first entity, and (ii) provide oneor more fields into which the user enters access information thatenables direct electronic access, by the first entity, to objects (e.g.,account information) representing the one or more existing relationships(e.g., accounts).

In some embodiments, in the step of generating, for provision to theuser, a second UI 606, the second UI may be configured to: (i) displayone or more relationship types and associated relationship informationregarding the one or more existing relationships that the user may wishto migrate, and (ii) provide one or more second UI elements configuredto allow the user to select at least one element representing the one ormore existing relationships with respect to which the user desires toreceive offer information regarding potential migration.

According to certain embodiments, in the step of generating, forprovision to the user, a third UI 610, the third UI may be configuredto: (i) display a comparison view illustrating the new relationshipterms of the one or more new relationships compared against existingrelationship terms of the one or more existing relationships that theuser selected for potential migration, and (ii) provide one or morethird UI elements selection of which by the user confirms that the userauthorizes relationship migration to proceed for selected ones of the atleast one element representing the one or more existing relationshipsselected for potential migration.

In some embodiments, the step of performing an automated relationshipgeneration process to create the new relationship(s) 612 may compriseperforming, upon receipt of the at least one element selectedrepresenting the one or more existing relationships, an automatedrelationship generation process that creates the one or more newrelationship authorized via user-selection of the one or more third UIelements. According to some aspects, the step of performing an automatedtransfer process to transfer all objects to the new relationship 614 maycomprise automatically performing a transfer process, by the at leastone computer accessing at least one application programming interface(API) of at least one computer platform associated with the secondentities, via an external network connection, including: (i) generatingelectronic requests to transfer all objects associated with a respectiveexisting relationship to the first entity; (ii) associating thetransferred objects with a respective new relationship associating withthe second entity; and (iii) confirming that the transferred objectshave been transferred.

In accordance with one particular illustrative implementation of themigration method 600 of FIG. 6, the one or more existing relationshipsmay comprise one or more existing accounts (e.g., financial accounts,etc.), the one or more new relationships may comprise one or more newaccounts, the one or more relationship types may comprise one or moreaccount types (e.g., checking, savings, etc.), the relationshipinformation may comprises new account information, the new relationshipterms may comprise new account terms, the existing relationship termsmay comprise existing account terms, the relationship migration maycomprises account migration, the automated relationship generationprocess may comprise an automated account generation process, and therelationship termination process may comprise an account terminationprocess. In some implementations, the new account terms compared againstthe existing account terms in the comparison view comprise one or moreof a fee (e.g., monthly account fee, service fee, etc.), an interestrates, an account type, and one or more terms associated with eachaccount being compared.

In another implementation related to such particular account migrationinnovations, the migration method 600 may further comprise: determining,via the direct electronic access of the one or more existing accounts bythe at least one computer, at least one recurring transaction among aplurality of charges of the one or more existing accounts; andautomatically initiating a transfer process related to transferring theat least one recurring transaction to at least one respective newaccount. Here, for example, in some embodiments, such transfer processmay comprise one or both of: (i) displaying the at least one recurringtransaction to the user with an interactive element that enables theuser to migrate the at least one recurring transaction to the at leastone respective new account; and (ii) automatically migrating the atleast one recurring transaction to the at least one respective newaccount.

In still other implementations related to such particular accountmigration innovations, the at least one computer associated withproviding the portal may automatically query, once the account accessinformation is received, account types and account balances from the oneor more existing accounts that the user selected for the potentialmigration. Similarly, with regard to such account migration innovations,one migration method 600 may further comprise generating, for provisionto the user, another UI configured to: (i) display one or more UIelements configured to receive identifying information regarding theuser; and (ii) confirm, upon submission of the identifying information,an actual identity of the user based on analysis of the identifyinginformation. One example of a UI configured for receiving suchuser-identifying information is shown and described further below inconnection with FIG. 7H.

According to other account migration innovations, as shown and describedin connection with FIG. 7D below, the migration method 600 may furthercomprise providing, to the user: (i) a list of financial institutionsfrom which migrations of accounts to the first entity are possible, and(ii) one or more interactive UI elements that enable the user to selectat which of the financial institutions on the list the user has one ormore existing accounts. Further, in some embodiments, the first UI maycomprise: an initial screen (e.g., FIG. 7D) comprising a list of all ofthe second entities regarding which account migration to the firstentity is supported, wherein selection of a second entity from the listautomatically navigates the user to a second screen (e.g., FIG. 7E)having fields to receive login access credentials of the user foraccessing the second entity online. The processing performed toestablish candidate accounts for possible migration may also includeutilization of the APIs 510 described above in connection with FIG. 5.Here, for example, the process of acquiring a list of user accounts thatare available for migration to the first entity (referred to as an“account acquisition process”) may be performed by an applicationprogramming interface (API) of at least one computer associated with thefirst entity. In some embodiments, such account acquisition process mayinclude: (i) receiving a first list of at least one of the secondentities at which at least one existing account of the user is held;(ii) determining at least one second entity, from the first list of atleast one of the second entities, regarding which the first entitysupports account migration; and (iii) presenting a second list ofaccounts that the user has at the at least one second entity such thataccounts on the second list are displayed as selectable items, whereinselection of an account from the second list selects the account for thepotential migration.

According to still other implementations, the migration method 600 mayfurther comprise, as part of the confirming that the balances/funds havebeen transferred, generating a fifth UI, for transmission to the user,confirming that the one or more new accounts have been opened and thatthe balances have been transferred. One example of such fifth UI isshown and described further, below, in connection with FIG. 7K.

Finally, the at least one computer associated with the first entity mayexecute various different instructions in automatically initiating orautomatically causing a relationship termination process of the existingrelationship(s) that are migrated, at 616. In one embodiments, forexample, the relationship or account deletion process may compriseautomatically transmitting, by the one or more computers associated withthe first entity, electronic communications to the second entitiesassociated with the one or more existing accounts that were successfullymigrated to the first entity, to close the one or more existing accountsthat were successfully migrated. Further, according to certain otherembodiments, the relationship or account termination process may beperformed (1) automatically, e.g., by one or more computers associatedwith the first entity, (2) manually, e.g., by action of the user, or (3)via a process that includes by automated processing performed bycomputer as well as manual action or interaction of the user.

Many banks require accounts to be closed through specific channels, mostcommonly via a phone call, or an email exchange. While the overallprocess of closing an account is fairly simple, it is tiered such thateach phase must ensure both sides of the conversation are in agreementto progress to the next stage. According to certain embodiments herein,the step of automatically causing a relationship or account terminationprocess 616 may comprise various advancements in text-to-speech andnatural language processing that enable the process to be more fullyautomated. In some embodiments, such innovations and feature may beimplemented through the utilization of commercially available CloudMachine Learning API's. In one aspect, for example, implementationscould include, though not limited by, use of Google's Cloud NaturalLanguage API. According to one specific example of such functionality,first, personal authentication information must be provided (e.g., firstname, last name, security questions, account number, etc.). Then, whenthe handshake is completed and the user has been validated, theintention (e.g., terminate account) must be made clear. Finally, thelast phase is the institution issuing a confirmation. The newadvancements in sentiment analysis, entity analysis, contentclassification, and syntax analysis has greatly reduced the riskassociated with commissioning an automated software application tohandle conversational tasks with a clear objective. Accordingly,consistent with the above features, embodiments herein are able totransform the previously manual termination process, often requiring aphone call or email exchange, into an automated process. Suchinnovations provide systems and methods herein with additionalcapabilities for automating relationship or account termination orclosure processes on behalf of the end user.

FIGS. 7A-7K are diagrams illustrating various exemplary user interfaces,features and functionality for performing migration of one or morerelationships or accounts, consistent with exemplary aspects of certainembodiments of the present disclosure.

As discussed above, embodiments herein may include providing a portaland/or generating various user interfaces for performing migration ofone or more relationships or accounts, from one or more existingentities, to a first entity or institution. FIG. 7A depicts an exampleof a login or sign-in screen 700 that may comprise a first field 702 forlogin credentials, a button 704 to sign in based on the credentialsentered, and other related UI options, such as a toggle switch toremember the user, an option to recover or reset login is the userforgot their login information, and the like, as associated with knownuser login screens. In some embodiments, different login credentials mayalso be utilized to sign in, such as credentials associated with arelated, known or trusted entity, user fingerprint, other biometricinformation, or the like. Once signed-in, the portal may present theuser with a first screen 705, which may provide the user with variousinformation 706 regarding the migration tool or process (e.g., ‘What itis’, ‘How it works’, etc.), Terms and Conditions for use of themigration tool 708, a button or selection 710 to confirm acceptance ofthe Terms and Conditions, and a button or option to proceed 712. FIG. 7Cdepicts an example of a user having selected the button to accept theTerms and Conditions, at 711, and the user selecting the continue button712 to proceed, e.g., to the screen shown in FIG. 7D, once theinformation is reviewed and the Terms and Conditions accepted.

FIG. 7D depicts an example of a first screen 713 of an illustrativemigration process, which provides functionality for the user to identifythe institutions or banks where they have relationships and/or accounts,which the user may desire to migrate to the first entity. Referring toFIG. 7D, the first screen 713 may comprise: a search field 714, such asa search bar for entering a text search, enabling the user to search forthe institution or bank where they have one or more existingrelationships or accounts; a list of known and/or common banks 716,which may include a number of options that the user may select by simplyclicking or selecting an entry corresponding to the institution wherethey have a relationship or account; and one or more additional optionsor tools 720 that provide functionality for the user to identify adesired institution of theirs, e.g., when they are unable to locate itby searching for it or selecting it, e.g., from the list of institutionsprovided at 716. The first screen 713 may also include a scroll bar orscrolling functionality 718, or similar UI mechanism, that enables theuser to quickly scroll through a list of institutions or banks beingoffered as potential entities where the user has relationships oraccounts. Once the user locates an institution, such as “The Bank” shownin the first screen 713, the user may select the institution name or aUI element corresponding to that institution, at 719. Upon suchselection, the portal will proceed with providing one or more screens toidentify the relationships or accounts at that institution for potentialmigration, e.g., beginning with FIG. 7E.

FIG. 7E depicts an example of a second screen 725 of an illustrativemigration process, which provides functionality for the user to provide,within the portal of the first entity, the login information (e.g.,username and password, etc.) utilized by the first entity toautomatically login to the institution of the user selected in FIG. 7D.Here, for example, the portal may generate a login credentials field722, including one or more fields 724 for the user to enter their logininformation and a sign in button or option 726 to proceed with login.Next, as shown in FIG. 7F, the portal may generate a third screen 727,which includes details of the user's relationships or accounts at theselected institution. Referring to the illustrative embodiment shown inFIG. 7F, for example, the exemplary third screen 727 may comprise arelationship or account summary field 728, which may include a listing730 of the various relationships and/or accounts that the user has withthat institution, as well as a button or option to ‘select all’relationships or accounts. In some embodiments, the relationships oraccounts may be selectable by the user (e.g., by touching or clickingthe account name) and/or may include a button or other UI element thatenables the user to select each relationship or account for furtherprocessing. FIG. 7G illustrates the results of such user interaction toselect the relationships or accounts for possible migration, accordingto one embodiment, indicating the accounts that were selected bydisplaying checkmarks 736 at the right of each relationship or accountentry on the list. The exemplary third screen 727 of FIGS. 7F and 7G mayalso include another button or option 732 to continue with the migrationprocessing, e.g., once the desired relationships or accounts have beenselected by the user.

FIG. 7H depicts an example of a fourth screen 735 of an illustrativemigration process, which provides functionality for the user to enterand submit their identifying information, such as confidential userinformation that may be needed to transfer a relationship or accountfrom one financial institution to another. Referring to FIG. 7H, anexemplary fourth screen 735 may be utilized by the portal to collectimportant personal information regarding the user that's required tomigrate the relationships or accounts to the first entity. The fourthscreen 735 may comprise an information entry interface 738 as well as acontinue button 742 used to proceed with the migration process once theinformation is entered. The information entry interface 738 may comprisea plurality of data fields for completion by the user. According to theone illustrative embodiment shown in FIG. 7H, for example, the datafields may include name (which may be pre-populated), date of birth,social security number, and country of citizenship. Different oradditional fields may be used or needed according to variousembodiments.

Once the user information is submitted via the fourth screen 735 and theinformation/user authenticated via one or more computer systemsassociated with the first entity, the portal may generate a fifth screen745, an example of which is illustrated in FIG. 7I. In one embodimentshown in FIG. 7I, the portal may generate, as the fifth screen 745, arelationship or account comparison and confirmation interface. Referringto FIG. 7I, an example fifth screen 745 may comprise a comparison field743 divided into two halves 744, 750 as well as a continue button 756 orlike UI element used to proceed to the next screen. The comparison field743 may comprise a first half 744 for displaying a list of all theexisting relationships or accounts being proposed for migration as wellas a second half 750 for displaying the list of the new relationships oraccounts being offered as replacements. Each entry of the existingrelationships or accounts as well as the replacement relationships oraccounts may comprise comparative information including graphicalindicia 746 and/or alpha-numeric information 748. The alpha-numericinformation 748 may comprise various terms and conditions regarding therelationship or account, such as interest rate, monthly fee, and/orother data points suitable for comparison. Once the user has assessedthis comparative information provided via the fifth screen 745 andindicated to continue 756, the portal will generate a sixth screen 755for the user to review and confirm acceptance of the migration, as setforth in connection with FIG. 7J.

FIG. 7J depicts an example of a sixth screen 755 of an illustrativemigration process, enabling the user to review a summary of the proposedmigration and associated information and select whether or not they wishto accept the proposed migration according to the terms generated anddisplayed to them via the portal. In the exemplary embodiment shown inFIG. 7J, the sixth screen 755 may comprise a review pane 758 and afinish button 764 or like UI element to proceed if the user agrees tothe migration. In some embodiments, the review pane 758 may include anew relationship or account summary field 760 and a user informationfield 762. The new relationship or account summary field 760 is used toprovide a summary of terms regarding the relationship or accounts beingoffered as well as a list of assets, such as bank balance(s), beingtransferred from the existing entity to the new entity via themigration. The user information field 762 is used to provide a summaryof the information regarding the user, e.g., to again help confirm thatthe migration is being performed for and authorized by the correctindividual.

Upon agreeing with the relationship/account migration being offered, theuser selects the finish button 764 and proceeds to a seventh screen 765that displays confirmation or results of the migration. In the exemplaryembodiment shown in FIG. 7K, the seventh screen 765 may comprise aconfirmation pane 770 that includes a summary of the new relationshipsor accounts that have been created to replace the old accounts migratedto the first entity. The summary of new relationships or accounts maycomprise, for example, display fields 722A,722B that display textualsummaries of the new relationships or accounts created.

FIG. 8 depicts a block diagram of an exemplary computer-basedsystem/platform in accordance with one or more embodiments of thepresent disclosure. However, not all of these components may be requiredto practice one or more embodiments, and variations in the arrangementand type of the components may be made without departing from the spiritor scope of various embodiments of the present disclosure. In someembodiments, the exemplary inventive computing devices and/or theexemplary inventive computing components of the exemplary computer-basedsystem/platform may be configured to manage a large number of members(e.g., clients, and their users) and/or concurrent interactions, asdetailed herein. In some embodiments, the exemplary computer-basedsystem/platform may be based on a scalable computer and/or networkarchitecture that incorporates varies strategies for assessing the data,caching, searching, and/or database connection pooling. An example ofthe scalable architecture is an architecture that is capable ofoperating multiple servers.

In some embodiments, referring to FIG. 8, members 702-704 (e.g.,clients) of the exemplary computer-based system/platform may includevirtually any computing device capable of receiving and sending amessage over a network (e.g., organization intranet, cloud network,etc.), such as network 705, to and from another computing device, suchas servers 706 and 707, each other, and the like. In some embodiments,the member devices 702-704 may be personal computers, multiprocessorsystems, microprocessor-based or programmable consumer electronics,network PCs, and the like. In some embodiments, one or more memberdevices within member devices 702-704 may include computing devices thattypically connect using a wireless communications medium such as cellphones, smart phones, pagers, walkie talkies, radio frequency (RF)devices, infrared (IR) devices, CBs, integrated devices combining one ormore of the preceding devices, or virtually any mobile computing device,and the like. In some embodiments, one or more member devices withinmember devices 702-704 may be devices that are capable of connectingusing a wired or wireless communication medium such as a PDA, POCKET PC,wearable computer, a laptop, tablet, desktop computer, a netbook, avideo game device, a pager, a smart phone, an ultra-mobile personalcomputer (UMPC), and/or any other device that is equipped to communicateover a wired and/or wireless communication medium (e.g., NFC, RFID,NBIOT, 3G, 4G, 5G, GSM, GPRS, WiFi, WiMax, CDMA, satellite, ZigBee,etc.). In some embodiments, one or more member devices within memberdevices 702-704 may include may run one or more applications, such asInternet browsers, mobile applications, voice calls, video games,videoconferencing, and email, among others. In some embodiments, one ormore member devices within member devices 702-704 may be configured toreceive and to send web pages, and the like. In some embodiments, anexemplary specifically programmed network/web browser application of thepresent disclosure may be configured to receive and display graphics,text, multimedia, and the like, employing virtually any web basedlanguage, including, but not limited to Standard Generalized MarkupLanguage (SMGL), such as HyperText Markup Language (HTML), a wirelessapplication protocol (WAP), a Handheld Device Markup Language (HDML),such as Wireless Markup Language (WML), WMLScript, XML, JavaScript, andthe like. In some embodiments, a member device within member devices702-704 may be specifically programmed by either Java, .Net, QT, C, C++and/or other suitable programming language. In some embodiments, one ormore member devices within member devices 702-704 may be specificallyprogrammed include or execute an application to perform a variety ofpossible tasks, such as, without limitation, messaging functionality,browsing, searching, playing, streaming or displaying various forms ofcontent, including locally stored or uploaded messages, images and/orvideo, and/or games.

In some embodiments, the exemplary network 705 may provide networkaccess, data transport and/or other services to any computing devicecoupled to it. In some embodiments, the exemplary network 705 mayinclude and implement at least one specialized network architecture thatmay be based at least in part on one or more standards set by, forexample, without limitation, GlobalSystem for Mobile communication (GSM)Association, the Internet Engineering Task Force (IETF), and theWorldwide Interoperability for Microwave Access (WiMAX) forum. In someembodiments, the exemplary network 705 may implement one or more of aGSM architecture, a General Packet Radio Service (GPRS) architecture, aUniversal Mobile Telecommunications System (UMTS) architecture, and anevolution of UMTS referred to as Long Term Evolution (LTE). In someembodiments, the exemplary network 705 may include and implement, as analternative or in conjunction with one or more of the above, a WiMAXarchitecture defined by the WiMAX forum. In some embodiments and,optionally, in combination of any embodiment described above or below,the exemplary network 705 may also include, for instance, at least oneof a local area network (LAN), a wide area network (WAN), the Internet,a virtual LAN (VLAN), an enterprise LAN, a layer 3 virtual privatenetwork (VPN), an enterprise IP network, or any combination thereof. Insome embodiments and, optionally, in combination of any embodimentdescribed above or below, at least one computer network communicationover the exemplary network 705 may be transmitted based at least in parton one of more communication modes such as but not limited to: NFC,RFID, Narrow Band Internet of Things (NBIOT), ZigBee, 3G, 4G, 5G, GSM,GPRS, WiFi, WiMax, CDMA, satellite and any combination thereof. In someembodiments, the exemplary network 705 may also include mass storage,such as network attached storage (NAS), a storage area network (SAN), acontent delivery network (CDN) or other forms of computer- ormachine-readable media.

In some embodiments, the exemplary server 706 or the exemplary server707 may be a web server (or a series of servers) running a networkoperating system, examples of which may include but are not limited toMicrosoft Windows Server, Novell NetWare, or Linux. In some embodiments,the exemplary server 706 or the exemplary server 707 may be used forand/or provide cloud and/or network computing. Although not shown inFIG. 8, in some embodiments, the exemplary server 706 or the exemplaryserver 707 may have connections to external systems like email, SMSmessaging, text messaging, ad content providers, etc. Any of thefeatures of the exemplary server 706 may be also implemented in theexemplary server 707 and vice versa.

In some embodiments, one or more of the exemplary servers 706 and 707may be specifically programmed to perform, in non-limiting example, asauthentication servers, search servers, email servers, social networkingservices servers, SMS servers, IM servers, MMS servers, exchangeservers, photo-sharing services servers, advertisement providingservers, financial/banking-related services servers, travel servicesservers, or any similarly suitable service-base servers for users of themember computing devices 701-704.

In some embodiments and, optionally, in combination of any embodimentdescribed above or below, for example, one or more exemplary computingmember devices 702-704, the exemplary server 706, and/or the exemplaryserver 707 may include a specifically programmed software module thatmay be configured to send, process, and receive information using ascripting language, a remote procedure call, an email, a tweet, ShortMessage Service (SMS), Multimedia Message Service (MMS), instantmessaging (IM), internet relay chat (IRC), mIRC, Jabber, an applicationprogramming interface, Simple Object Access Protocol (SOAP) methods,Common Object Request Broker Architecture (CORBA), HTTP (HypertextTransfer Protocol), REST (Representational State Transfer), or anycombination thereof.

FIG. 9 depicts a block diagram of another exemplary computer-basedsystem/platform 800 in accordance with one or more embodiments of thepresent disclosure. However, not all of these components may be requiredto practice one or more embodiments, and variations in the arrangementand type of the components may be made without departing from the spiritor scope of various embodiments of the present disclosure. In someembodiments, the member computing devices 802 a, 802 b thru 802 n showneach at least includes a computer-readable medium, such as arandom-access memory (RAM) 808 coupled to a processor 810 or FLASHmemory. In some embodiments, the processor 810 may executecomputer-executable program instructions stored in memory 808. In someembodiments, the processor 810 may include a microprocessor, an ASIC,and/or a state machine. In some embodiments, the processor 810 mayinclude, or may be in communication with, media, for examplecomputer-readable media, which stores instructions that, when executedby the processor 810, may cause the processor 810 to perform one or moresteps described herein. In some embodiments, examples ofcomputer-readable media may include, but are not limited to, anelectronic, optical, magnetic, or other storage or transmission devicecapable of providing a processor, such as the processor 810 of client802 a, with computer-readable instructions. In some embodiments, otherexamples of suitable media may include, but are not limited to, a floppydisk, CD-ROM, DVD, magnetic disk, memory chip, ROM, RAM, an ASIC, aconfigured processor, all optical media, all magnetic tape or othermagnetic media, or any other medium from which a computer processor canread instructions. Also, various other forms of computer-readable mediamay transmit or carry instructions to a computer, including a router,private or public network, or other transmission device or channel, bothwired and wireless. In some embodiments, the instructions may comprisecode from any computer-programming language, including, for example, C,C++, Visual Basic, Java, Python, Perl, JavaScript, and etc.

In some embodiments, member computing devices 802 a-n may also comprisea number of external or internal devices such as a mouse, a CD-ROM, DVD,a physical or virtual keyboard, a display, or other input or outputdevices. In some embodiments, examples of member computing devices 802a-n (e.g., clients) may be any type of processor-based platforms thatare connected to a network 806 such as, without limitation, personalcomputers, digital assistants, personal digital assistants, smartphones, pagers, digital tablets, laptop computers, Internet appliances,and other processor-based devices. In some embodiments, member computingdevices 802 a-n may be specifically programmed with one or moreapplication programs in accordance with one or moreprinciples/methodologies detailed herein. In some embodiments, membercomputing devices 802 a-n may operate on any operating system capable ofsupporting a browser or browser-enabled application, such as Microsoft™,Windows™, and/or Linux. In some embodiments, member computing devices802 a-n shown may include, for example, personal computers executing abrowser application program such as Microsoft Corporation's InternetExplorer™, Apple Computer, Inc.'s Safari™, Mozilla Firefox, and/orOpera. In some embodiments, through the member computing client devices802 a-n, users, 812 a-n, may communicate over the exemplary network 806with each other and/or with other systems and/or devices coupled to thenetwork 806. As shown in FIG. 9, exemplary server devices 804 and 813may be also coupled to the network 806. In some embodiments, one or moremember computing devices 802 a-n may be mobile clients.

In some embodiments, at least one database of exemplary databases 807and 815 may be any type of database, including a database managed by adatabase management system (DBMS). In some embodiments, an exemplaryDBMS-managed database may be specifically programmed as an engine thatcontrols organization, storage, management, and/or retrieval of data inthe respective database. In some embodiments, the exemplary DBMS-manageddatabase may be specifically programmed to provide the ability to query,backup and replicate, enforce rules, provide security, compute, performchange and access logging, and/or automate optimization. In someembodiments, the exemplary DBMS-managed database may be chosen fromOracle database, IBM DB2, Adaptive Server Enterprise, FileMaker,Microsoft Access, Microsoft SQL Server, MySQL, PostgreSQL, and a NoSQLimplementation. In some embodiments, the exemplary DBMS-managed databasemay be specifically programmed to define each respective schema of eachdatabase in the exemplary DBMS, according to a particular database modelof the present disclosure which may include a hierarchical model,network model, relational model, object model, or some other suitableorganization that may result in one or more applicable data structuresthat may include fields, records, files, and/or objects. In someembodiments, the exemplary DBMS-managed database may be specificallyprogrammed to include metadata about the data that is stored.

As also shown in FIGS. 9 and 10, some embodiments of the disclosedtechnology may also include and/or involve one or more cloud components825, which are shown grouped together in the drawing for sake ofillustration, though may be distributed in various ways as known in theart. Cloud components 825 may include one or more cloud services such assoftware applications (e.g., queue, etc.), one or more cloud platforms(e.g., a Web front-end, etc.), cloud infrastructure (e.g., virtualmachines, etc.), and/or cloud storage (e.g., cloud databases, etc.).

According to some embodiments shown by way of one example in FIG. 11,the exemplary inventive computer-based systems/platforms, the exemplaryinventive computer-based devices, components and media, and/or theexemplary inventive computer-implemented methods of the presentdisclosure may be specifically configured to operate in or with cloudcomputing/architecture such as, but not limiting to: infrastructure aservice (IaaS) 1010, platform as a service (PaaS) 1008, and/or softwareas a service (SaaS) 1006. FIGS. 10 and 11 illustrate schematics ofexemplary implementations of the cloud computing/architecture(s) inwhich the exemplary inventive computer-based systems/platforms, theexemplary inventive computer-implemented methods, and/or the exemplaryinventive computer-based devices, components and/or media of the presentdisclosure may be specifically configured to operate. In someembodiments, such cloud architecture 1006, 1008, 1010 may be utilized inconnection with the web browser and network aspects, shown at 1004, toachieve the innovations herein.

As used in the description and in any claims, the term “based on” is notexclusive and allows for being based on additional factors notdescribed, unless the context clearly dictates otherwise. In addition,throughout the specification, the meaning of “a,” “an,” and “the”include plural references. The meaning of “in” includes “in” and “on.”

It is understood that at least one aspect/functionality of variousembodiments described herein can be performed in real-time and/ordynamically. As used herein, the term “real-time” is directed to anevent/action that can occur instantaneously or almost instantaneously intime when another event/action has occurred. For example, the “real-timeprocessing,” “real-time computation,” and “real-time execution” allpertain to the performance of a computation during the actual time thatthe related physical process (e.g., a user interacting with anapplication on a mobile device) occurs, in order that results of thecomputation can be used in guiding the physical process.

As used herein, the term “dynamically” and term “automatically,” andtheir logical and/or linguistic relatives and/or derivatives, mean thatcertain events and/or actions can be triggered and/or occur without anyhuman intervention. In some embodiments, events and/or actions inaccordance with the present disclosure can be in real-time and/or basedon a predetermined periodicity of at least one of: nanosecond, severalnanoseconds, millisecond, several milliseconds, second, several seconds,minute, several minutes, hourly, several hours, daily, several days,weekly, monthly, etc.

As used herein, the term “runtime” corresponds to any behavior that isdynamically determined during an execution of a software application orat least a portion of software application.

In some embodiments, exemplary inventive, specially programmed computingsystems/platforms with associated devices are configured to operate inthe distributed network environment, communicating with one another overone or more suitable data communication networks (e.g., the Internet,satellite, etc.) and utilizing one or more suitable data communicationprotocols/modes such as, without limitation, IPX/SPX, X.25, AX.25,AppleTalk™, TCP/IP (e.g., HTTP), Bluetooth™, near-field wirelesscommunication (NFC), RFID, Narrow Band Internet of Things (NBIOT), 3G,4G, 5G, GSM, GPRS, WiFi, WiMax, CDMA, satellite, ZigBee, and othersuitable communication modes. Various embodiments herein may includeinteractive posters that involve wireless, e.g., Bluetooth™ and/or NFC,communication aspects, as set forth in more detail further below. Insome embodiments, the NFC can represent a short-range wirelesscommunications technology in which NFC-enabled devices are “swiped,”“bumped,” “tap” or otherwise moved in close proximity to communicate. Insome embodiments, the NFC could include a set of short-range wirelesstechnologies, typically requiring a distance of 10 cm or less. In someembodiments, the NFC may operate at 13.56 MHz on ISO/IEC 18000-3 airinterface and at rates ranging from 106 kbit/s to 424 kbit/s. In someembodiments, the NFC can involve an initiator and a target; theinitiator actively generates an RF field that can power a passivetarget. In some embodiment, this can enable NFC targets to take verysimple form factors such as tags, stickers, key fobs, or cards that donot require batteries. In some embodiments, the NFL's peer-to-peercommunication can be conducted when a plurality of NFC-enable devices(e.g., smartphones) are within close proximity of each other.

The material disclosed herein may be implemented in software or firmwareor a combination of them or as instructions stored on a machine-readablemedium, which may be read and executed by one or more processors. Amachine-readable medium may include any medium and/or mechanism forstoring or transmitting information in a form readable by a machine(e.g., a computing device). For example, a machine-readable medium mayinclude read only memory (ROM); random access memory (RAM); magneticdisk storage media; optical storage media; flash memory devices;electrical, optical, acoustical or other forms of propagated signals(e.g., carrier waves, infrared signals, digital signals, etc.), andothers.

As used herein, the terms “computer engine” and “engine” identify atleast one software component and/or a combination of at least onesoftware component and at least one hardware component which aredesigned/programmed/configured to manage/control other software and/orhardware components (such as the libraries, software development kits(SDKs), objects, etc.).

Examples of hardware elements may include processors, microprocessors,circuits, circuit elements (e.g., transistors, resistors, capacitors,inductors, and so forth), integrated circuits, application specificintegrated circuits (ASIC), programmable logic devices (PLD), digitalsignal processors (DSP), field programmable gate array (FPGA), logicgates, registers, semiconductor device, chips, microchips, chip sets,and so forth. In some embodiments, the one or more processors may beimplemented as a Complex Instruction Set Computer (CISC) or ReducedInstruction Set Computer (RISC) processors; x86 instruction setcompatible processors, multi-core, or any other microprocessor orcentral processing unit (CPU). In various implementations, the one ormore processors may be dual-core processor(s), dual-core mobileprocessor(s), and so forth.

Examples of software may include software components, programs,applications, computer programs, application programs, system programs,machine programs, operating system software, middleware, firmware,software modules, routines, subroutines, functions, methods, procedures,software interfaces, application program interfaces (API), instructionsets, computing code, computer code, code segments, computer codesegments, words, values, symbols, or any combination thereof.Determining whether an embodiment is implemented using hardware elementsand/or software elements may vary in accordance with any number offactors, such as desired computational rate, power levels, heattolerances, processing cycle budget, input data rates, output datarates, memory resources, data bus speeds and other design or performanceconstraints.

One or more aspects of at least one embodiment may be implemented byrepresentative instructions stored on a machine-readable medium whichrepresents various logic within the processor, which when read by amachine causes the machine to fabricate logic to perform the techniquesdescribed herein. Such representations, known as “IP cores” may bestored on a tangible, machine readable medium and supplied to variouscustomers or manufacturing facilities to load into the fabricationmachines that make the logic or processor. Of note, various embodimentsdescribed herein may, of course, be implemented using any appropriatehardware and/or computing software languages (e.g., C++, Objective-C,Swift, Java, JavaScript, Python, Perl, QT, etc.).

In some embodiments, one or more of exemplary inventive computer-basedsystems/platforms, exemplary inventive computer-based devices, and/orexemplary inventive computer-based components of the present disclosuremay include or be incorporated, partially or entirely into at least onepersonal computer (PC), laptop computer, ultra-laptop computer, tablet,touch pad, portable computer, handheld computer, palmtop computer,personal digital assistant (PDA), cellular telephone, combinationcellular telephone/PDA, television, smart device (e.g., smart phone,smart tablet or smart television), mobile internet device (MID),messaging device, data communication device, and so forth.

As used herein, term “server” should be understood to refer to a servicepoint which provides processing, database, and communication facilities.By way of example, and not limitation, the term “server” can refer to asingle, physical processor with associated communications and datastorage and database facilities, or it can refer to a networked orclustered complex of processors and associated network and storagedevices, as well as operating software and one or more database systemsand application software that support the services provided by theserver. Cloud components (e.g., FIG. 3-4) and cloud servers areexamples.

In some embodiments, as detailed herein, one or more of exemplaryinventive computer-based systems/platforms, exemplary inventivecomputer-based devices, and/or exemplary inventive computer-basedcomponents of the present disclosure may obtain, manipulate, transfer,store, transform, generate, and/or output any digital object and/or dataunit (e.g., from inside and/or outside of a particular application) thatcan be in any suitable form such as, without limitation, a file, acontact, a task, an email, a tweet, a map, an entire application (e.g.,a calculator), etc. In some embodiments, as detailed herein, one or moreof exemplary inventive computer-based systems/platforms, exemplaryinventive computer-based devices, and/or exemplary inventivecomputer-based components of the present disclosure may be implementedacross one or more of various computer platforms such as, but notlimited to: (1) AmigaOS, AmigaOS 4; (2) FreeBSD, NetBSD, OpenBSD; (3)Linux; (4) Microsoft Windows; (5) OpenVMS; (6) OS X (Mac OS); (7) OS/2;(8) Solaris; (9) Tru64 UNIX; (10) VM; (11) Android; (12) Bada; (13)BlackBerry OS; (14) Firefox OS; (15) Ios; (16) Embedded Linux; (17) PalmOS; (18) Symbian; (19) Tizen; (20) WebOS; (21) Windows Mobile; (22)Windows Phone; (23) Adobe AIR; (24) Adobe Flash; (25) Adobe Shockwave;(26) Binary Runtime Environment for Wireless (BREW); (27) Cocoa (API);(28) Cocoa Touch; (29) Java Platforms; (30) JavaFX; (31) JavaFX Mobile;(32) Microsoft XNA; (33) Mono; (34) Mozilla Prism, XUL and XULRunner;(35) .NET Framework; (36) Silverlight; (37) Open Web Platform; (38)Oracle Database; (39) Qt; (40) SAP NetWeaver; (41) Smartface; (42) Vexi;and/OR (43) Windows Runtime.

In some embodiments, exemplary inventive computer-basedsystems/platforms, exemplary inventive computer-based devices, and/orexemplary inventive computer-based components of the present disclosuremay be configured to utilize hardwired circuitry that may be used inplace of or in combination with software instructions to implementfeatures consistent with principles of the disclosure. Thus,implementations consistent with principles of the disclosure are notlimited to any specific combination of hardware circuitry and software.For example, various embodiments may be embodied in many different waysas a software component such as, without limitation, a stand-alonesoftware package, a combination of software packages, or it may be asoftware package incorporated as a “tool” in a larger software product.

For example, exemplary software specifically programmed in accordancewith one or more principles of the present disclosure may bedownloadable from a network, for example, a website, as a stand-aloneproduct or as an add-in package for installation in an existing softwareapplication. For example, exemplary software specifically programmed inaccordance with one or more principles of the present disclosure mayalso be available as a client-server software application, or as aweb-enabled software application. For example, exemplary softwarespecifically programmed in accordance with one or more principles of thepresent disclosure may also be embodied as a software package installedon a hardware device.

In some embodiments, exemplary inventive computer-basedsystems/platforms, exemplary inventive computer-based devices, and/orexemplary inventive computer-based components of the present disclosuremay be configured to output to distinct, specifically programmedgraphical user interface implementations of the present disclosure(e.g., a desktop, a web app., etc.). In various implementations of thepresent disclosure, a final output may be displayed on a displayingscreen which may be, without limitation, a screen of a computer, ascreen of a mobile device, or the like. In various implementations, thedisplay may be a holographic display. In various implementations, thedisplay may be a transparent surface that may receive a visualprojection. Such projections may convey various forms of information,images, and/or objects. For example, such projections may be a visualoverlay for a mobile augmented reality (MAR) application.

In some embodiments, exemplary inventive computer-basedsystems/platforms, exemplary inventive computer-based devices, and/orexemplary inventive computer-based components of the present disclosuremay be configured to be utilized in various applications which mayinclude, but not limited to, gaming, mobile-device games, video chats,video conferences, live video streaming, video streaming and/oraugmented reality applications, mobile-device messenger applications,and others similarly suitable computer-device applications.

As used herein, the term “mobile electronic device,” or the like, mayrefer to any portable electronic device that may or may not be enabledwith location tracking functionality (e.g., MAC address, InternetProtocol (IP) address, or the like). For example, a mobile electronicdevice can include, but is not limited to, a mobile phone, PersonalDigital Assistant (PDA), Blackberry™, Pager, Smartphone, smart watch, orany other reasonable mobile electronic device.

As used herein, terms “proximity detection,” “locating,” “locationdata,” “location information,” and “location tracking” refer to any formof location tracking technology or locating method that can be used toprovide a location of, for example, a particular computingdevice/system/platform of the present disclosure and/or any associatedcomputing devices, based at least in part on one or more of thefollowing techniques/devices, without limitation: accelerometer(s),gyroscope(s), Global Positioning Systems (GPS); GPS accessed usingBluetooth™; GPS accessed using any reasonable form of wireless and/ornon-wireless communication; WiFi™ server location data; Bluetooth™ basedlocation data; triangulation such as, but not limited to, network basedtriangulation, WiFi™ server information based triangulation, Bluetooth™server information based triangulation; Cell Identification basedtriangulation, Enhanced Cell Identification based triangulation,Uplink-Time difference of arrival (U-TDOA) based triangulation, Time ofarrival (TOA) based triangulation, Angle of arrival (AOA) basedtriangulation; techniques and systems using a geographic coordinatesystem such as, but not limited to, longitudinal and latitudinal based,geodesic height based, Cartesian coordinates based; Radio FrequencyIdentification such as, but not limited to, Long range RFID, Short rangeRFID; using any form of RFID tag such as, but not limited to active RFIDtags, passive RFID tags, battery assisted passive RFID tags; or anyother reasonable way to determine location. For ease, at times the abovevariations are not listed or are only partially listed; this is in noway meant to be a limitation.

As used herein, terms “cloud,” “Internet cloud,” “cloud computing,”“cloud architecture,” and similar terms correspond to at least one ofthe following: (1) a large number of computers connected through areal-time communication network (e.g., Internet); (2) providing theability to run a program or application on many connected computers(e.g., physical machines, virtual machines (VMs)) at the same time; (3)network-based services, which appear to be provided by real serverhardware, and are in fact served up by virtual hardware (e.g., virtualservers), simulated by software running on one or more real machines(e.g., allowing to be moved around and scaled up (or down) on the flywithout affecting the end user).

The aforementioned examples are, of course, illustrative and notrestrictive.

As used herein, the term “user” shall have a meaning of at least oneuser. In some embodiments, the terms “user”, “subscriber”, “consumer”,or “customer” should be understood to refer to a user of an applicationor applications as described herein and/or a consumer of data suppliedby a data provider. By way of example, and not limitation, the terms“user” or “subscriber” can refer to a person who receives data providedby the data or service provider over the Internet in a browser session,or can refer to an automated software application which receives thedata and stores or processes the data.

At least some aspects of the present disclosure will now be describedwith reference to the following numbered clauses.

Clause 1. A computer-implemented method comprising:

providing, by at least one computer associated with a first entity, aportal by which a user may be provided functionality to migrate, to thefirst entity, one or more existing relationships that the user has withone or more second entities;

generating, by the at least one computer, for provision to the user, afirst UI configured to:

-   -   (i) display one or more first UI elements that enable the user        to specify the one or more existing relationships that the user        may wish to migrate to the first entity, and    -   (ii) provide one or more fields into which the user enters        access information that enables direct electronic access, by the        first entity, to objects representing the one or more existing        relationships;

generating, by the at least one computer, for provision to the user, asecond UI configured to:

-   -   (i) display one or more relationship types and associated        relationship information regarding the one or more existing        relationships that the user may wish to migrate, and    -   (ii) provide one or more second UI elements configured to allow        the user to select at least one element representing the one or        more existing relationships with respect to which the user        desires to receive offer information regarding potential        migration;

determining by the at least one computer, new relationship terms of oneor more new relationships that the first entity can offer the user, theone or more new relationships corresponding to the one or more existingrelationships that the user selected for the potential migration to thefirst entity;

generating, by the at least one computer, for provision to the user, athird UI configured to:

-   -   (i) display a comparison view illustrating the new relationship        terms of the one or more new relationships compared against        existing relationship terms of the one or more existing        relationships that the user selected for potential migration,        and    -   (ii) provide one or more third UI elements selection of which by        the user confirms that the user authorizes relationship        migration to proceed for selected ones of the at least one        element representing the one or more existing relationships        selected for potential migration;

upon receipt of the at least one element selected representing the oneor more existing relationships, performing, by the at least onecomputer, an automated relationship generation process that creates theone or more new relationship authorized via user-selection of the one ormore third UI elements; and

automatically performing a transfer process, by the at least onecomputer accessing at least one application programming interface (API)of at least one computer platform associated with the second entities,via an external network connection, including:

-   -   (i) generating electronic requests to transfer all objects        associated with a respective existing relationship to the first        entity;    -   (ii) associating the transferred objects with a respective new        relationship associating with the second entity; and    -   (iii) confirming that the transferred objects have been        transferred; and

automatically causing, by the at least one computer, a relationshiptermination process of the one or more existing relationship toterminate each respective transferred existing relationship with thesecond entity that was successfully transferred to the first entity.

Clause 2. The method of clause 1 or the innovations of any clauseherein, wherein the one or more existing relationships comprise one ormore existing accounts, the one or more new relationships comprise oneor more new accounts, the one or more relationship types comprise one ormore account types, the relationship information comprises accountinformation, the new relationship terms comprise new account terms, theexisting relationship terms comprise existing account terms, therelationship migration comprises account migration, the automatedrelationship generation process comprises an automated accountgeneration process, and the relationship termination process comprisesan account termination process.Clause 3. The method of clause 2 or the innovations of any clauseherein, wherein the new account terms compared against the existingaccount terms in the comparison view comprise one or more of a fee, aninterest rates, an account type, and one or more terms associated witheach account being compared.Clause 4. The method of clause 3 or the innovation of any clause herein,further comprising:

determining, via the direct electronic access of the one or moreexisting accounts by the at least one computer, at least one recurringtransaction among a plurality of charges of the one or more existingaccounts; and automatically initiating a transfer process related totransferring the at least one recurring transaction to at least onerespective new account, the transfer process comprising one or both of:(i) displaying the at least one recurring transaction to the user withan interactive element that enables the user to migrate the at least onerecurring transaction to the at least one respective new account; and(ii) automatically migrating the at least one recurring transaction tothe at least one respective new account.

Clause 5. The method of clause 2 or the innovation of any clause herein,wherein the at least one computer automatically queries, once theaccount access information is received, account types and accountbalances from the one or more existing accounts that the user selectedfor the potential migration.Clause 6. The method of clause 2 or the innovation of any clause herein,further comprising:

generating, for provision to the user, another UI configured to: (i)display one or more UI elements configured to receive identifyinginformation regarding the user; and (ii) confirm, upon submission of theidentifying information, an actual identity of the user based onanalysis of the identifying information.

Clause 7. The method of clause 2 or the innovation of any clause herein,further comprising:

providing, to the user: (i) a list of financial institutions from whichmigrations of accounts to the first entity are possible, and (ii) one ormore interactive UI elements that enable the user to select at which ofthe financial institutions on the list the user has one or more existingaccounts.

Clause 8. The method of clause 2 or the innovation of any clause herein,wherein the first UI comprises:

an initial screen comprising a list of all of the second entitiesregarding which account migration to the first entity is supported,wherein selection of a second entity from the list automaticallynavigates the user to a second screen having fields to receive loginaccess credentials of the user for accessing the second entity online.

Clause 9. The method of clause 2 or the innovation of any clause herein,further comprising, as part of the confirming that the balances/fundshave been transferred:

generating a fifth UI, for transmission to the user, confirming that theone or more new accounts have been opened and that the balances havebeen transferred.

Clause 10. The method of clause 1 or the innovation of any clauseherein, further comprising:

performing an account acquisition process, by an application programminginterface (API) of at least one first computer associated with the firstentity, including:

-   -   (i) receiving a first list of at least one of the second        entities at which at least one existing account of the user is        held;    -   (ii) determining at least one second entity, from the first list        of at least one of the second entities, regarding which the        first entity supports account migration; and    -   (iii) presenting a second list of accounts that the user has at        the at least one second entity such that accounts on the second        list are displayed as selectable items, wherein selection of an        account from the second list selects the account for the        potential migration.        Clause 11. The method of clause 2 or the innovation of any        clause herein, wherein the account deletion process comprises:

automatically transmitting, by the one or more computers associated withthe first entity, electronic communications to the second entitiesassociated with the one or more existing accounts that were successfullymigrated to the first entity, to close the one or more existing accountsthat were successfully migrated.

Clause 12. The method of clause 2 or the innovation of any clauseherein, wherein the account termination process is performed by one orboth of: automatically, by one or more computers associated with thefirst entity, and manually, by the user.Clause 13. A computer-implemented method comprising:

providing, by at least one computer associated with a first entity, aportal by which a user may be provided functionality to migrate, to thefirst entity, one or more existing accounts that the user has at one ormore second entities;

generating, by the at least one computer, for provision to the user, afirst UI configured to:

-   -   (i) display one or more first UI elements that enable the user        to specify the one or more existing accounts that the user may        wish to migrate to the first entity, and    -   (ii) provide one or more fields into which the user enters        account access information that enables direct electronic        access, by the first entity, to the one or more existing        accounts;        -   wherein the at least one computer automatically queries,            once the account access information is received, account            types and account balances from the one    -   or more existing accounts that the user selected for the        potential migration;

generating, by the at least one computer, for provision to the user, asecond UI configured to:

-   -   (i) display one or more account types and associated account        information including the account balances regarding the one or        more existing accounts that the user may wish to migrate, and    -   (ii) provide one or more second UI elements configured to allow        the user to select the one or more existing accounts with        respect to which the user desires to receive offer information        regarding potential migration;

determining by the at least one computer, new account terms of one ormore new accounts that the first entity can offer the user, the one ormore new accounts corresponding to the one or more existing accountsthat the user selected for the potential migration to the first entity;

generating, by the at least one computer, for provision to the user, athird UI configured to:

-   -   (i) display a comparison view illustrating the new account terms        of the one or more new accounts compared against existing        account terms of the one or more existing accounts that the user        selected for potential migration, and    -   (ii) provide one or more third UI elements selection of which by        the user confirms that the user authorizes account migration to        proceed for selected ones of the one or more existing accounts        selected for potential migration;

upon receipt of the selected ones of the one or more existing accounts,performing, by the at least one computer, an automated accountgeneration process that creates the one or more new accounts authorizedvia user-selection of the one or more third UI elements; and

automatically performing a transfer process, by the at least onecomputer accessing at least one application programming interface (API)of at least one computer platform associated with the second entities,via an external network connection, including:

-   -   (i) generating electronic requests to transfer all balances to        the first entity;    -   (ii) depositing the balances into the one or more new accounts        created at the first entity; and    -   (iii) confirming that the balances have been transferred; and

automatically executing, by the at least one computer, an accounttermination process of the one or more existing accounts to terminateeach respective transferred existing account that was successfullytransferred to the first entity.

Clause 14. The method of clause 13 or the innovation of any clauseherein, wherein the new account terms compared against the existingaccount terms in the comparison view comprise one or more of a fee, aninterest rates, an account type, and one or more terms associated witheach account being compared.Clause 15. The method of clause 14 or the innovation of any clauseherein, further comprising:

determining, via the direct electronic access of the one or moreexisting accounts by the at least one computer, at least one recurringtransaction among a plurality of charges of the one or more existingaccounts; and

automatically initiating a transfer process related to transferring theat least one recurring transaction to at least one respective newaccount, the transfer process comprising one or both of: (i) displayingthe at least one recurring transaction to the user with an interactiveelement that enables the user to migrate the at least one recurringtransaction to the at least one respective new account; and (ii)automatically migrating the at least one recurring transaction to the atleast one respective new account.

Clause 16. The method of clause 13 or the innovation of any clauseherein, further comprising:

generating, for provision to the user, another UI configured to: (i)display one or more UI elements configured to receive identifyinginformation regarding the user; and (ii) confirm, upon submission of theidentifying information, an actual identity of the user based onanalysis of the identifying information.

Clause 17. The method of clause 13 or the innovation of any clauseherein, further comprising:

providing, to the user: (i) a list of financial institutions from whichmigrations of accounts to the first entity are possible, and (ii) one ormore interactive UI elements that enable the user to select at which ofthe financial institutions on the list the user has one or more existingaccounts.

Clause 18. The method of clause 13 or the innovation of any clauseherein, wherein the first UI comprises:

an initial screen comprising a list of all of the second entitiesregarding which account migration to the first entity is supported,wherein selection of a second entity from the list automaticallynavigates the user to a second screen having fields to receive loginaccess credentials of the user for accessing the second entity online.

Clause 19. The method of clause 13 or the innovation of any clauseherein, further comprising, as part of the confirming that thebalances/funds have been transferred:

generating a fifth UI, for transmission to the user, confirming that theone or more new accounts have been opened and that the balances havebeen transferred.

Clause 20. The method of clause 13 or the innovation of any clauseherein, further comprising:

performing an account acquisition process, by an application programminginterface (API) of at least one first computer associated with the firstentity, including:

-   -   (i) receiving a first list of at least one of the second        entities at which at least one existing account of the user is        held;    -   (ii) determining at least one second entity, from the first list        of at least one of the second entities, regarding which the        first entity supports account migration; and    -   (iii) presenting a second list of accounts that the user has at        the at least one second entity such that accounts on the second        list are displayed as selectable items, wherein selection of an        account from the second list selects the account for the        potential migration.        Clause 21. The method of clause 13 or the innovation of any        clause herein, wherein the account deletion process comprises:

automatically transmitting, by the one or more computers associated withthe first entity, electronic communications to the second entitiesassociated with the one or more existing accounts that were successfullymigrated to the first entity, to close the one or more existing accountsthat were successfully migrated.

Clause 22. The method of clause 13 or the innovation of any clauseherein, wherein the account termination process is performed by one orboth of: automatically, by one or more computers associated with thefirst entity, and manually, by the user.Clause 20. Embodiments herein may also take the form of a systemcomprised of computing elements that are arranged, programmed and/orotherwise adapted to perform the features and functionality set forthanywhere above.Clause 21. In addition, embodiments herein may also take the form of oneor more computer readable media containing computer-executableinstructions for performing any of the processing herein, thecomputer-executable instructions being executable via one or moreprocessing components to process instructions and/or perform one or moreaspects of the functionality set forth herein.

While one or more embodiments of the present disclosure have beendescribed, it is understood that these embodiments are illustrativeonly, and not restrictive, and that many modifications may becomeapparent to those of ordinary skill in the art, including that variousembodiments of the inventive methodologies, the inventivesystems/platforms, and the inventive devices described herein can beutilized in any combination with each other. Further still, the varioussteps may be carried out in any desired order (and any desired steps maybe added and/or any desired steps may be eliminated).

1. A computer-implemented method comprising: providing, by a firstcomputer directly associated with a first entity, to a computing deviceassociated with a user, a portal which is configured to allow the userto instruct an automatic electronic account migration of at least onecurrent user account to the first computer associated with the firstentity, via a network, from at least one second computer associated withone or more second entities that are unrelated to the first entity;executing, by the first computer directly associated with the firstentity, a relationship acquisition process of at least one existingrelationship from the one or more second entities, wherein therelationship acquisition process includes: receiving, by the firstcomputer directly associated with the first entity via the portal, fromthe computing device associated with the user, user account accessinformation for the at least one current user account so as to enablethe first computer to establish a direct electronic access to digitalobjects associated with the at least one current user account at the atleast one second computer associated with one or more second entities,the digital objects representing the at least one current user accountand one or more existing electronic relationships associated with the atleast one current user account within the at least one second computer;automatically establishing, by the first computer directly associatedwith the first entity, a direct communication between the first computerdirectly associated with the first entity and the at least one secondcomputer associated with the one or more second entities to access tothe digital objects based on the current user account access informationand implemented via one or more inter-entity application programminginterfaces (APIs) of the at least one second computer associated withthe one or more second entities, the inter-entity APIs being configuredfor communication between the first entity and the one or more secondentities; determining, by the first computer directly associated withthe first entity via the one or more inter-entity APIs and over thenetwork, from the digital objects at the at least one second computer,account information of the at least one current user account and the oneor more existing relationships associated with the at least one currentuser account wherein the determining includes establishing, by theinter-entity APIs, a set of the one or more relationships that areaccessible and configured to provide migration information, via theinter-entity APIs, that is relevant to assessing and implementingmigration to the first entity; and providing, to the first entity, a setof the one or more second entities that correspond to the set of the oneor more relationships established as being accessible and configured toprovide the migration information via the inter-entity APIs; generating,by the first computer, a first UI, and providing the first UI, via thenetwork, to the computing device associated with the user, the first UIbeing configured to allow the user to instruct the automatic electronicaccount migration of the at least one current user account andcomprising: (i) one or more first UI elements configured to allow theuser to at least see a) account data of the at least one current useraccount and b) at least one of the one or more existing relationshipsassociated with the at least one current user account, and (ii) one ormore additional UI elements configured to allow the user to define oneor more account-related migration parameters and select the one or moreexisting relationships that the user desires to be migrated with the atleast one current user account; processing selection of the one or morefirst UI elements and the one or more additional UI elements, bothprovided by the user, so as to form, together, an automatic electronicaccount migration instruction; receiving, by the first computer directlyassociated with the first entity via the portal, from the computingdevice associated with the user, the automatic electronic accountmigration instruction to migrate the at least one current user accountfrom the at least one second computer associated with one or more secondentities; utilizing, by the at least one first computer, the accessinformation, to establish the direct electronic access, via the one ormore inter-entity APIs and the network, to the one or more digitalobjects to obtain one or more relationship types and associatedrelationship information regarding the one or more existingrelationships, wherein the one or more digital objects are accessedwhile the user is in a un-logged in state with regard to the secondcomputer associated with the second entity; automatically generating, bythe first computer, a second UI, and providing the second UI to thecomputing device associated with the user, the second UI comprising (i)the one or more relationship types and the associated relationshipinformation regarding the one or more existing relationships that theuser wishes to migrate, wherein the one or more relationship types andthe associated relationship information are returned by the inter-entityAPIs and displayed, via the portal provided by the first entity, fordirect visual comparison with one or more new relationship terms of oneor more new relationships that the first entity offers to the user, and(ii) one or more second UI elements configured to allow the user to atleast view, at the first computer, new account data of the at least onenew user account and the one or more new relationships at the firstcomputer processing selection of the one or more second UI elementsselected by the user; automatically determining by the at least onefirst computer, the one or more new relationship terms of one or morenew relationships that the first entity otters to the user, wherein theone or more new relationships correspond to the at least one migratingcandidate; generating, by the at least one computer, a third UI, andproviding the third UI to the computing device associated with the user,wherein the third UI comprises: (i) a comparison view illustrating theat least one new relationship terms of the one or more new relationshipscompared against at least one existing relationship terms of the atleast one migrating candidate relationship, and (ii) one or more thirdUI elements selection of which by the user confirms that the userauthorizes relationship migration to proceed for selected ones of the atleast one element representing the at least one migrating candidaterelationship selected; processing, by the at least one computer inresponse to selections of the one or more third UI elements selected bythe user, a selection of the at least one element selected representingthe at least one migrating candidate relationship; automaticallyperforming, by the at least one computer in response to the at least oneelement selected by the user and received, an automated relationshipgeneration process that creates the one or more new relationshipsauthorized via user-selection of the one or more third UI elements;automatically instructing, by the first computer directly associatedwith the first entity, via the one or more inter-entity APIs and overthe network, based on the automatic electronic account migrationinstruction, the at least one second computer to perform a transferprocess, via an external network connection, the transfer processincluding: (i) generating electronic requests to transfer all objectsassociated with a respective existing relationship of the at least onemigrating candidate to the first entity; (ii) associating thetransferred objects with a respective new relationship of the one ormore new relationships provided by the first entity; (iii) transferringcontent of the at least one current user account to at the firstcomputer; (iv) transferring relationship data for one or more selectedexisting relationships associated with the at least one current useraccount to the first computer; and (v) confirming that the transferredcontent and relationship data have been transferred; and automaticallyestablishing, by the first computer directly associated with the firstentity, at least one new user account and one or more new relationshipsassociated with that at least one new user account at the first computerbased on the transferred content of the at least one current useraccount and the relationship data for the one or more selected existingrelationships; and automatically instructing, by the first computerdirectly associated with the first entity, via the one or moreinter-entity APIs and over the network, based on the automaticelectronic account migration instruction, the at least one secondcomputer to perform a relationship termination process of the at leastone migrating candidate relationship to terminate each respectivetransferred existing relationship with the second entity that wassuccessfully transferred to the first entity, including: (i) terminatingthe at least one current user account at the at least one secondcomputer; and (ii) terminating the one or more selected existingrelationships associated with the at least one current user at the atleast one second computer.
 2. The method of claim 1 wherein the one ormore existing relationships comprise one or more existing accounts, theone or more new relationships comprise one or more new accounts, the oneor more relationship types comprise one or more account types, therelationship information comprises account information, the newrelationship terms comprise new account terms, the existing relationshipterms comprise existing account terms, the relationship migrationcomprises account migration, the automated relationship generationprocess comprises an automated account generation process, and therelationship termination process comprises an account terminationprocess.
 3. The method of claim 2 wherein the new account terms comparedagainst the existing account terms in the comparison view comprise oneor more of a fee, an interest rates, an account type, and one or moreterms associated with each account being compared.
 4. The method ofclaim 3 further comprising: determining, via the direct electronicaccess of the one or more existing accounts via accessing theinter-entity APIs by the at least one computer, at least one recurringtransaction among a plurality of charges of the one or more existingaccounts; and automatically initiating a transfer process related totransferring the at least one recurring transaction to at least onerespective new account, the transfer process comprising one or both of:(i) displaying the at least one recurring transaction to the user withan interactive element that enables the user to migrate the at least onerecurring transaction to the at least one respective new account; and(ii) automatically migrating the at least one recurring transaction tothe at least one respective new account.
 5. (canceled)
 6. The method ofclaim 2, further comprising: generating, for provision to the user,another UI configured to: (i) display one or more UI elements configuredto receive identifying information regarding the user; and (ii) confirm,upon submission of the identifying information, an actual identity ofthe user based on analysis of the identifying information.
 7. The methodof claim 2, further comprising: providing, to the user: (i) a list offinancial institutions from which migrations of accounts to the firstentity are possible, mid (ii) one or more interactive UI elements thatenable the user to select at which of the financial institutions on thelist the user has one or more existing accounts.
 8. The method of claim2, wherein the first UI comprises: an initial screen comprising a listof all of the second entities regarding which account migration to thefirst entity is supported, wherein selection of a second entity from thelist automatically navigates the user to a second screen having fieldsto receive login access credentials of the user for accessing the secondentity online.
 9. The method of claim 2, further comprising, as part ofthe confirming that the transferred objects have been transferred:generating a fifth UI, for transmission to the user, confirming that theone or more new accounts have been opened and that the balances havebeen transferred.
 10. The method of claim 2 further comprising:performing an account acquisition process, by an application programminginterface (API) of at least one first computer associated with the firstentity, including: (i) receiving a first list of at least one of thesecond entities at which at least one existing account of the user isheld; (ii) determining at least one second entity, from the first listof at least one of the second entities, regarding which the first entitysupports account migration; and (iii) presenting a second list ofaccounts that the user has at the at least one second entity such thataccounts on the second list are displayed as selectable items, whereinselection of an account from the second list selects the account for thepotential migration.
 11. The method of claim 2, wherein the accountdeletion process comprises: automatically transmitting, by the one ormore computers associated with the first entity, electroniccommunications to the second entities associated with the one or moreexisting accounts that were successfully migrated to the first entity,to close the one or more existing accounts that were successfullymigrated.
 12. The method of claim 2 wherein the account terminationprocess is performed automatically, by one or more computers associatedwith the first entity.
 13. A computer-implemented method comprising:providing, by a first computer directly associated with a first entity,to a computing device associated with a user, a portal which isconfigured to allow the user to instruct an automatic electronic accountmigration of at least one current user account to the first computerassociated with the first entity, via a network, from at least onesecond computer associated with one or more second entities that areunrelated to the first entity; executing, by the first computer directlyassociated with the first entity, an account acquisition process of atleast one existing account from the one or more second entities, whereinthe account acquisition process includes: receiving, by the firstcomputer directly associated with the first entity via the portal, fromthe computing device associated with the user, user account accessinformation for the at least one current user account so as to enablethe first computer to establish a direct electronic access to digitalobjects associated with the at least one current user account at the atleast one second computer associated with one or more second entities,the digital objects representing the at least one current user accountand one or more existing electronic relationships associated with the atleast one current user account within the at least one second computer;automatically establishing, by the first computer directly associatedwith the first entity, a direct communication between the first computerdirectly associated with the first entity and the at least one secondcomputer associated with the one or more second entities to access tothe digital objects based on the current user account access informationand implemented via one or more inter-entity application programminginterfaces (APIs) of the at least one second computer associated withthe one or more second entities, the inter-entity APIs being configuredfor communication between the first entity and the one or more secondentities; determining, by the first computer directly associated withthe first entity via the inter-entity APIs and over the network, fromthe digital objects at the at least one second computer, accountinformation of the at least one current user account and the one or moreexisting accounts associated with the at least one current user accountwherein the determining includes establishing, by the inter-entity APIs,a set of the one or more relationships that are accessible andconfigured to provide migration information, via the inter-entity APIs,that is relevant to assessing and implementing migration to the firstentity; and providing, to the first entity, a set of the one or moresecond entities that correspond to the set of the one or morerelationships established as being accessible and configured to providethe migration information via the inter-entity APIs; generating, by thefirst computer, a first UI, and providing the first UI, via the network,to the computing device associated with the user, the first UI beingconfigured to allow the user to instruct the automatic electronicaccount migration of the at least one current user account andcomprising: (i) one or more first UI elements configured to allow theuser to at least see a) account data of the at least one current useraccount and b) at least one of the one or more existing relationshipsassociated with the at least one current user account, and (ii) one ormore additional UI elements configured to allow the user to define oneor more account-related migration parameters and select the one or moreexisting relationships that the user desires to be migrated with the atleast one current user account; wherein the at least one computerautomatically queries, once the account access information is received,account types and account balances from the one or more existingaccounts that the user selected for the potential migration; processingselection of the one or more first UI elements and the one or moreadditional UI elements, both provided by the user, so as to form,together, an automatic electronic account migration instruction;receiving, by the first computer directly associated with the firstentity via the portal, from the computing device associated with theuser, the automatic electronic account migration instruction to migratethe at least one current user account from the at least one secondcomputer associated with one or more second entities; utilizing, by theat least one first computer, the access information, to establish thedirect electronic access, via the one or more inter-entity APIs and thenetwork, to the one or more digital objects to obtain one or moreaccount types and associated account information regarding the one ormore existing accounts, wherein the one or more digital objects areaccessed while the user is in a un-logged in state with regard to thesecond computer associated with the second entity; automaticallygenerating, by the first computer, a second UI, and providing the secondUI to the computing device associated with the user, the second UIcomprising: (i) the one or more account types and the associated accountinformation including the account balances regarding the one or moreexisting accounts that the user wishes to migrate, wherein the one ormore relationship types and the associated relationship information arereturned by the inter-entity APIs and displayed, via the portal providedby the first entity, for direct visual comparison with one or more newrelationship terms of one or more new relationships that the firstentity offers to the user, and (ii) one or more second UI elementsconfigured to allow the user to at least view, at the first computer,new account data of the at least one new user account and the one ormore new relationships at the first computer; processing selection ofthe one or more second UI elements selected by the user; automaticallydetermining by the first computer, the one or more new account terms ofone or more new accounts that the first entity offers to the user,wherein the one or more new accounts correspond to the at least onemigrating candidate accounts; generating, by the at least one computer,a third UI, and providing the third UI to the computing deviceassociated with the user, wherein the third UI comprises: (i) acomparison view illustrating the at least one new account term of theone or more new accounts compared against at least one existing accountterm of the at least one migrating candidate accounts, and (ii) one ormore third UI elements selection of which by the user confirms that theuser authorizes account migration to proceed for selected ones of theone or more at least one migrating candidate accounts selected;processing, by the at least one computer in response to selections ofthe one or more third UI elements selected by the user, a selection ofthe at least one dement selected representing the at least one migratingcandidate relationship; automatically performing, by the at least onecomputer in response to the at least one element selected by the userand received, an automated relationship generation process that createsthe one or more new relationships authorized via user-selection of theone or more third UI elements; and automatically instructing, by thefirst computer directly associated with the first entity, via the one ormore inter-entity APIs and over the network, based on the automaticelectronic account migration instruction, the at least one secondcomputer to perform a transfer process, via an external networkconnection, the transfer process including: (i) generating electronicrequests to transfer all balances to the first entity; (ii) depositingthe balances into the one or more new accounts created at the firstentity; (iii) transferring content of the at least one current useraccount to at the first computer; (iv) transferring relationship datafor one or more selected existing relationships associated with the atleast one current user account to the first computer; and (v) confirmingthat the balances have been transferred; and automatically establishing,by the first computer directly associated with the first entity, atleast one new user account and one or more new relationships associatedwith that at least one new user account at the first computer based onthe transferred content of the at least one current user account and therelationship data for the one or more selected existing relationships;and automatically instructing, by the first computer directly associatedwith the first entity, via the one or more inter-entity APIs and overthe network, based on the automatic electronic account migrationinstruction, the at least one second computer to perform an accounttermination process of the of the at least one migrating candidateaccounts to terminate each respective transferred existing account thatwas successfully transferred to the first entity, including: (i)terminating the at least one current user account at the at least onesecond computer; and (ii) terminating the one or more selected existingrelationships associated with the at least one current user at the atleast one second computer.
 14. The method of claim 13 wherein the newaccount terms compared against the existing account terms in thecomparison view comprise one or more of a fee, an interest rates, anaccount type, and one or more terms associated with each account beingcompared.
 15. The method of claim 14 further comprising: determining,via the direct electronic access of the one or more existing accountsvia accessing the inter-entity APIs by the at least one computer, atleast one recurring transaction among a plurality of charges of the oneor more existing accounts; and automatically initiating a transferprocess related to transferring the at least one recurring transactionto at least one respective new account, the transfer process comprisingone or both of: (i) displaying the at least one recurring transaction tothe user with an interactive element that enables the user to migratethe at least one recurring transaction to the at least one respectivenew account; and (ii) automatically migrating the at least one recurringtransaction to the at least one respective new account.
 16. The methodof claim 13, further comprising: generating, for provision to the user,another UI configured to: (i) display one or more UI elements configuredto receive identifying information regarding the user; and (ii) confirm,upon submission of the identifying information, an actual identity ofthe user based on analysis of the identifying information.
 17. Themethod of claim 13, further comprising: providing, to the user: (i) alist of financial institutions from which migrations of accounts to thefirst entity are possible, and (ii) one or more interactive UI elementsthat enable the user to select at which of the financial institutions onthe list the user has one or more existing accounts.
 18. The method ofclaim 13, wherein the first UI comprises: an initial screen comprising alist of all of the second entities regarding which account migration tothe first entity is supported, wherein selection of a second entity fromthe list automatically navigates the user to a second screen havingfields to receive login access credentials of the user for accessing thesecond entity online.
 19. The method of claim 13, further comprising, aspart of the confirming that the balances/funds have been transferred:generating a firth UI, for transmission to the user, confirming that theone or more new accounts have been opened and that the balances havebeen transferred.
 20. The method of claim 13 further comprising:performing an account acquisition process, by an application programminginterface (API) of at least one first computer associated with the firstentity, including: (i) receiving a first list of at least one of thesecond entities at which at least one existing account of the user isheld; (ii) determining at least one second entity, from the first listof at least one of the second entities, regarding which the first entitysupports account migration; and (iii) presenting a second list ofaccounts that the user has at the at least one second entity such thataccounts on the second list are displayed as selectable items, whereinselection of an account from the second list selects the account for thepotential migration.
 21. The method of claim 6, further comprising:providing, to the user: (i) a list of financial institutions from whichmigrations of accounts to the first entity are possible, and (ii) one ormore interactive UI elements that enable the user to select at which ofthe financial institutions on the list the user has one or more existingaccounts.